Skip to content

Conversation

@pre-commit-ci
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Nov 18, 2024

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from d6cdc3d to db14e91 Compare November 25, 2024 22:17
updates:
- [github.com/astral-sh/ruff-pre-commit: v0.7.3 → v0.8.1](astral-sh/ruff-pre-commit@v0.7.3...v0.8.1)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from db14e91 to 8d99f61 Compare December 2, 2024 22:42
@EZoni EZoni merged commit 6d64333 into development Dec 3, 2024
33 checks passed
@EZoni EZoni deleted the pre-commit-ci-update-config branch December 3, 2024 23:27
@EZoni EZoni restored the pre-commit-ci-update-config branch December 3, 2024 23:29
@EZoni
Copy link
Member

EZoni commented Dec 3, 2024

@WeiqunZhang

I just merged this simple PR (I wanted to do it before releasing 24.12) and I see that the "CI / 🔄 Update Stub Files / Stubs" check on development is failing. Do you have any idea why this might be happening?

@ax3l
Copy link
Member

ax3l commented Jan 2, 2025

@EZoni @WeiqunZhang this happens because for the final push of the updates stub files on development, we need specific permissions. Background:

Thus, currently, I have to use a personal access token (PAT), which is stored as a secret named PYAMREX_PUSH_TOKEN in this repo's settings and used here:

PAT's can only be valid for 366 days at a time and this one needed a refresh. I have done this today.

Long-term, I am interested to find a solution that can use the default secrets.GITHUB_TOKEN to avoid having to create a PAT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants